Hey! Your PR title Fix @ file indexing for junction/symlink directories on Windows doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Added a follow-up fix for the Windows unit timeout seen on this PR.

What changed:

• Replaced unconditional follow: true in File.scan() with a safer approach:
  • keep the normal non-follow Ripgrep.files({ cwd }) scan for the workspace
  • separately index root linked directories (symlink/junction) by scanning each link path directly
• Added dedupe guards for files/dirs and linked targets to avoid repeated traversal/cycle amplification.

Why:

• CI showed unit (windows) hanging in Run unit tests until job timeout.
• Global recursive follow over links can explode traversal on Windows junction-heavy trees.

Local validation:

• bun test --timeout 30000 test/file/index.test.ts -t "File.search()" (from packages/opencode)
• bun test --timeout 30000 test/file/ripgrep.test.ts (from packages/opencode)
• bun turbo test (repo root)
• pre-push hook bun turbo typecheck

Rebased this branch on latest and resolved conflicts caused by the file module refactor.\n\nWhat I changed:\n- ported the symlink/junction indexing fix from to (current implementation location)\n- kept the regression test for linked directories in \n- preserved case-insensitive dedupe on Windows and guarded linked-target traversal to avoid recursive loops\n\nThis should clear the merge conflict state and keep behavior aligned with current architecture.